README documentation for IBM Tivoli Monitoring for Version 6.3.0 Fix Pack 7 including installation-related instructions, prerequisites and corequisites, and list of fixes.
README file for: IBM Tivoli Monitoring
Product/Component Release:6.3.0
Update Name:Fix Pack 7
Fix ID: 6.3.0-TIV-ITM-FP0007
Publication date:January 06, 2017
Last modified date:January 06, 2017
Download location
Prerequisites and corequisites
Known issues
Known limitations
Installation information
Prior to installationLanguage Pack Installation information
Installing
Performing the necessary tasks after installation
Post installation security updates
Troubleshooting installation problems from the Support site
InstallingAdditional Information
Download IBM Tivoli Monitoring Version 6.3.0 Fix Pack 7 upgrade
images from the following location:
http://www.ibm.com/support/fixcentral/swg/quickorder?parent=ibm~Tivoli&product=ibm/Tivoli/IBM+Tivoli+Monitoring&release=All&platform=All&function=fixId&fixids=6.3.0-TIV-ITM-FP0007&source=fc
Alternatively, access the fix from the table below.
| Product/Component Name |
Platform |
File Name |
|---|---|---|
| IBM Tivoli Monitoring Base | 64-bit Windows | 6.3.0-TIV-ITM_TMV-Windows64-FP0007.zip |
| IBM Tivoli Monitoring Base | 32-bit Windows | 6.3.0-TIV-ITM_TMV-Windows-FP0007.zip |
| IBM Tivoli Monitoring Base | UNIX | 6.3.0-TIV-ITM_TMV-Unix-FP0007.tar.gz |
| IBM Tivoli Monitoring Base | 64-bit Linux(R) on AMD64 and Intel(R) EMT systems | 6.3.0-TIV-ITM_TMV-Linuxx64-FP0007.tar.gz |
| IBM Tivoli Monitoring Base | 32-bit Linux(R) on AMD and Intel(R) systems | 6.3.0-TIV-ITM_TMV-Linuxx-FP0007.tar.gz |
| IBM Tivoli Monitoring Base | Linux(R) on System z | 6.3.0-TIV-ITM_TMV-Linuxz-FP0007.tar.gz |
| IBM Tivoli Monitoring Base Agents | All | 6.3.0-TIV-ITM_TMV-Agents-FP0007.tar.gz |
| IBM Tivoli Monitoring Tools | All | 6.3.0-TIV-ITM_TMV-Tools-FP0007.tar.gz |
| IBM Tivoli Monitoring Agent Reports | All | 6.3.0-TIV-ITM_TMV-Agent-Reports-FP0007.tar.gz |
| IBM Tivoli Monitoring Tivoli Performance Analyzer Reports and Domain Definitions | All | 6.3.0-TIV-ITM_TMV-ITPA-Common-FP0007.tar.gz |
| Product/Component Name |
Platform |
File Name |
|---|---|---|
| IBM Tivoli Monitoring Language Pack | All | 6.3.0-TIV-ITM_TMV-LP-FP0006.gz |
| IBM Tivoli Monitoring Dashboards for Servers and Authorization Policy Components | All | 6.3.0-TIV-ITM_TMV-Dashboards-Authorization_Policy-FP0002.zip |
Download IBM Tivoli Monitoring Version 6.3.0 Fix Pack 7 pristine images from the IBM Passport Advantage® Online Website.
Tivoli Monitoring Software:
| Number of eAssembly to download |
Number of part to download |
Title on Passport Advantage |
Contents |
|---|---|---|---|
| CJ1ECML | CNH58EN | IBM Tivoli Monitoring V6.3.0.7 Base, Windows (32 Bit env.), English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support in English for base agents for 32-bit Windows operating systems |
| CJ1ECML | CNH59EN | IBM Tivoli Monitoring V6.3.0.7 Base, Windows (64 Bit env.), English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Windows operating systems |
| CJ1ECML | CNH5AEN | IBM Tivoli Monitoring V6.3.0.7 Base, Unix, English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for UNIX operating systems |
| CJ1ECML | CNH5BEN | IBM Tivoli Monitoring V6.3.0.7 Base, Linux (32 Bit Env.), English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 32-bit Env. Linux operating systems |
| CJ1ECML | CNH5CEN | IBM Tivoli Monitoring V6.3.0.7 Base, Linux (64 Bit Env.), English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for 64-bit Env. Linux operating systems |
| CJ1ECML | CNH5DEN | IBM Tivoli Monitoring V6.3.0.7 Base, Linux on System z®, English | Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Portal Client, Tivoli Data Warehouse agents, and application support for base agents in English for Linux on System z operating systems |
| CJ1ECML | CNH5EEN | IBM Tivoli Monitoring V6.3.0.7 Tools, Multiplatform, English | Tivoli Monitoring event synchronization component, Tivoli Enterprise Console® Event Definition Generator (TEDGEN) utility, and audit record DTDs |
| CJ1ECML | CN8CWML | IBM Tivoli Monitoring V6.3.0.6 Language Support | Language pack for Tivoli Monitoring server components, warehouse agents, OS agents, agentless OS agents, Tivoli Performance Analyzer agent for all operating systems and languages |
| CJ1ECML | CNH5FML | IBM Tivoli Performance Analyzer V6.3.0.7: Reports and Domain Definitions Multiplatform, Multilingual | Performance Analyzer domains and BIRT reports |
Tivoli Monitoring Agents and Agent Builder:
| Number of eAssembly to download |
Number of part to download |
Title on Passport Advantage |
Contents |
|---|---|---|---|
| CJ1EDML | CNH5GML | IBM Tivoli Monitoring V6.3.0.7 Agents, Multiplatform, Multilingual | Operating system agents (IBM i, Linux, UNIX, Windows) and Agentless OS agents (AIX, HP-UX, Linux, Solaris, Windows) |
| CJ1EDML | CNH5HML | IBM Tivoli Monitoring V6.3.0.7 Agent Reports | Operating system agent reports and reports installer |
| CJ1EDML | CN8GZML | IBM Tivoli Monitoring V6.3.2 Agent Builder Language Support | Language support files for Agent Builder |
| CJ1EDML | CN8HOEN | IBM Tivoli Monitoring V6.3.2 Agent Builder, English, Multiplatform | Agent Builder in English for multiple operating systems |
For a complete set of prerequisites, refer to the "Hardware and
software requirements" section in the IBM Tivoli Monitoring
Installation and Setup Guide Version 6.3.0 Fix Pack 2 available
at the following URL:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/install/install_itm.htm?lang=en
A number of platforms previously supported by IBM Tivoli Monitoring version 6.2.x are no longer supported by version 6.3.0 (and subsequent 6.3.0 fix packs). However these platforms will remain supported by version 6.2.x. agents connected to version 6.3.0 (or later) infrastructure. Also for no longer supported server platforms, support will remain utilizing version 6.2.x RTEMS connecting to version 6.3.0 (or later) HUB TEMS. See the IBM Tivoli Monitoring coexistence and interoperability section of the Installation and Setup Guide for detailed information.
Further, IBM Tivoli Monitoring version 6.3.0 (and subsequent fix packs) introduced a number of platform improvements which may require operating system updates. It is important that you ensure your systems meet these requirements prior to installing or updating your installation.Additional information:
The following technote contains tables showing these platform changes and requirements: http://www.ibm.com/support/docview.wss?uid=swg21623341.
The following issues have been found in a version of this
release, either in previous releases, or in this release. The
symptom and the workaround has been listed for each issue.
The following issues are unique to this fix pack.
When installing the pristine installation, additional messages will be seen.
Symptom:
This installation image contains the monitoring server or portal
server.
The monitoring server and portal server will not start with
separate installation and data directories.
If you want to install the monitoring server or portal server,
you must use the installation directory for data.
If you want to install a different component, you may specify a
different location for data.
Do you want to place data in the installation directory or
specify a different location?
[ 1-Use installation directory, 2-Specify another directory; "1"
is default ]
Additional information:
The new messages are a result of APAR IV67523 Move local data
from CANDLEHOME to another file system: http://www-01.ibm.com/support/docview.wss?uid=swg21695194
The following issues affected the IBM Tivoli Monitoring Monitoring 6.3.0 through 6.3.0 FP7 release and are still applicable to this fix pack.
Symptom:
Java 7.0 not working in Internet Explorer.
Additional information:
One or more of the following tips may apply: http://www.java.com/en/download/help/ie_tips.xml
The following limitations are unique to this fix pack.
None.
The following issues affected the IBM Tivoli Monitoring Monitoring 6.3.0 through 6.3.0 FP7 release and are still applicable to this fix pack.
Long path names in 6.3.0-TIV-ITM_TMV-Dashboards-Authorization_Policy-FP0002.zip
When expanding the 6.3.0-TIV-ITM_TMV-Dashboards-Authorization_Policy-FP0002.zip file on Windows, users may encounter a "Path too long" error. This typically occurs when the target extract location is located in a directory under the user's home folder, such as "C:\Documents and Settings\Administrator\My Documents". To resolve this issue, target the extraction to a top level directory with a shorter path, such as "C:\Temp".
Before proceeding with the installation process, please make note of these important points:
| $ITMHOME | 1200 MB |
| /tmp/ | 800 MB |
Run the pdcollect utility to gather all of the current logs and environment files. These backups can be used for reference, if needed, after the upgrade. The "tacmd pdcollect -help" command can be issued to obtain the syntax for the pdcollect utility.
If using the ITMSuper tool, run the tool to take a
snapshot of the entire ITM infrastructure prior to the
install of this fix pack.
Run the migrate-export.bat (Windows) or migrate-export.sh (UNIX/Linux) to backup the contents of the portal server database. This snapshot will allow for recovery of the database back to the point prior to installing this fix pack maintenance.
Run the pdcollect utility to gather all of the current logs and environment files. These backups can be used for reference, if needed, after the upgrade. The "tacmd pdcollect -help" command can be issued to obtain the syntax for the pdcollect utility.
If using the ITMSuper tool, run the tool to take a snapshot of the entire ITM infrastructure prior to the install of this fix pack.
If using the ITMSuper tool, it is recommended to run the tool after applying the fix pack to create snapshot of the entire ITM environment that can be compared to the baseline snapshot taken with ITMSuper before the installation. The baseline snapshot can be done by selecting the Topology, Connectivity, and TEMS Servers tabs and saving the session. Information about the ITMSuper tool can be found at the following URL:
http://www.ibm.com/software/brandcatalog/ismlibrary/details?catalog.label=1TW10TM6LYou can validate your installation by running the KinCInfo
command on Windows systems or the cinfo command on Linux or UNIX
systems. If you run these commands before and after your
upgrade, you can clearly see the component versions that have
changed.
For interim fixes, only components that have been updated during
this release have the latest listed level. If a component has
not been updated, the package will contain the most recent GA
copy. There is no need to upgrade this component if your system
is at the listed level, the install programs should
automatically handle this for you.
Note: The KinCInfo and cinfo command output examples in the
sections that follow show all components that can be updated. If
you do not have all of these components installed, then
components not installed will not be displayed in the output of
these commands.
Note: The "Monitoring agent for UNIX Logs" agent name has been
deprecated. Going forward, this agent will be named "UNIX Logs"
agent.
When applying IBM Tivoli Monitoring maintenance updates it is necessary to know if the corresponding baroc definition contained in the maintenance needs to be applied to the event integration server such as a Tivoli Enterprise Console Server or Netcool/OMNIbus Probe for Tivoli Event Integration Facility (EIF).
This fix pack contains baroc files at the level documented in the list below. If you have an earlier level installed you will need to reinstall them.
| IBM Tivoli Monitoring Infrastructure | ||
|---|---|---|
| Operations and Audit Log | kib.baroc | 06.30.02.00 |
| Remote Deploy | kdy.baroc | 06.21.00.00 |
| IBM Tivoli Monitoring Data Warehouse Agents | ||
| Warehouse Proxy | khd.baroc | 06.30.00.00 |
| Summarization and Pruning | ksy.baroc | 06.30.02.00 |
| IBM Tivoli Monitoring 6.x for OS Agents | ||
| Windows | knt.baroc | 06.30.07.00 |
| UNIX | kux.baroc | 06.30.07.00 |
| Linux | klz.baroc | 06.30.07.00 |
| i5/OS | ka4.baroc | 06.30.02.00 |
| IBM Tivoli Monitoring 6.x for Agentless OS Agents | ||
| Windows | kr2.baroc | 06.30.06.00 |
| AIX | kr3.baroc | 06.30.03.00 |
| Linux | kr4.baroc | 06.30.06.00 |
| HP | kr5.baroc | 06.30.03.00 |
| Solaris | kr6.baroc | 06.30.06.00 |
Recent security updates have been included in this Fix Pack including APARs IV74486 and IV77408. In addition to these, additional updates for the Tivoli Enterprise Portal and Tivoli Enterprise Portal Server (TEPS) need to be done to complete the remediation for the CVEs published at the time of the Fix Pack being released. See the technote below for more details.
http://www.ibm.com/support/docview.wss?uid=swg21960130
For additional troubleshooting help not covered in this README
document, please visit the IBM Tivoli Monitoring support page at
the following URL:
http://www.ibm.com/support/entry/portal/Overview/Software/Tivoli/Tivoli_Monitoring_V6
The language pack was last refreshed for IBM Tivoli Monitoring 6.3.0 Fix Pack 6.
Installing a language pack on a Windows system
To install a language pack, first make sure that you have already installed the product in English, then perform the following steps:
Note: You can hold down the Ctrl key for multiple selections.
Installing a language pack on a UNIX/Linux system
To install a language pack, first make sure that you have already installed the product in English, then perform the following steps:
mkdir <dir_name>
Note: Make sure that the full path of <dir_name> does not contain any spaces
cd <dir_name>
lpinstaller.sh -c ?candle_home>
Note: <candle_home> is where you installed IBM Tivoli Monitoring, usually it is /opt/IBM/ITM for AIX and Linux.
Note: You can hold down the Ctrl key for multiple selections.
This is a cumulative fix pack for IBM Tivoli Monitoring, Version 6.3.0. This fix pack supersedes all previous IBM Tivoli Monitoring versions, including GA Version 6.3.0. This fix pack can be installed in just one step on top of any level of IBM Tivoli Monitoring version 6.1, 6.2, 6.2.1, 6.2.2 or 6.2.3.
The IBM Tivoli approach for fix packs and interim fixes is to deliver regular, incremental quality improvements.The main areas of quality improvements made in this maintenance deliverable relative to the most recently shipped IBM Tivoli Monitoring release (IBM Tivoli Monitoring 6.3.0) are shown below.
The following new features are included in IBM Tivoli Monitoring 6.3.0 Fix Pack 7:
The following updates pertain to the online documentation:
http://www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/install/teps64.htm
<property name="jnlp.tep.connection.protocol" value="http"/>
Should read:
The statement:
Or you can create this install_dir/localconfig/pc/pc_confglist.xml file:
Should read:
Or you can create this install_dir/localconfig/pc/pc_cnfglist.xml file:
Changes to Configuring the Summarization and Pruning Agent (JDBC connection)
You can now select the HTTP and HTTPS protocols for JDBC connections. Also the TEPS userid and password are now required when configuring the connection. Please see the technote for APAR IV81519 for details.
| Agentless OS Monitor APARs | |
|---|---|
| IV73175 | Linux Agentless Network Bytes_In_per_sec and Bytes_Out_per_sec
sometimes reported as negative values. The problem can also occur
for the Solaris Agentless Agent |
| IV80811 | Increase in CPU after upgrading to Agentless 6.30 FP6. Extra
tracing was enabled which results in log messages being continually
written to the RAS1 log file. This can affect any of the Agentless
agents. The RAS1 log for the Agentless agent is filled with the following messages: (56A23C39.0FE9-2514:listcursor.cpp,72,"hasMoreElements") listcursor head = 86D1C8, cursor=86D258 (56A23C39.0FEA-2514:listcursor.cpp,56,"setToNext") listcursor head = 86D1C8, cursor=86D2E8 |
| IV83352 | This APAR allows the Agentless Monitoring agent to report the
hostname for the Managed System Status. This results in setting the
"hostname" slot in events to the hostname of the remote system
instead of the hostname where the Agentless Monitoring agent is
running. This fix affects all five Agentless Monitoring agents. |
| Basic Services APARs | |
| IV53175 | After event clearing, when Netcool/OMNIbus sends a CT_Reset with
a display item URL containing character string 'JAVASCRIPT', the
SOAP request is rejected with SOAP faultstring response "unable to
extract client data from posted request". |
| IV82451 | Transport Layer Security (TLS) cryptographic protocol is the
industry standard used for Secure Socket Layer (SSL) communication.
There is no product-provided means of setting or restricting the
versions of Transport Layer Security to TLS 1.0, 1.1 or 1.2 . In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IV86800 | TDS client fails using TLS v1.2 with Microsoft Active Directory
server. UserID authentication fails when trying to logon to
monitoring server via tacmd CLI or via portal client. The monitoring
server integrates with TDS client 6.3.0.27. The issue is that TDS
client connects with Microsoft Active Directory server using the
protocol TLSV1.2. When we set the parameter
LDAP_OPT_SECURITY_PROTOCOL to change the protocol to TLS v1.0 or
TLSv1.1 TDS client can connect with AD server successfully.
Monitoring Server 6.30 FP5 and FP6 use TDS client: 6.3.0.27 and
GSKit 8.0.50.36. |
| IV87524 | Code in the Tivoli (Basic Services) HTTP server is noncompliant
with RFC 7230. Whitespace between the the start-line and the first
header field is not processed correctly. This leaves the IBM Tivoli
Monitoring process vulnerable to the 'Whitespace ("Hosts of
Trouble") vulnerability'. |
| Command Line Interface APARs | |
| IV74282 | HUB monitoring server may crash during shutdown if monitoring
server SOAP service did not complete start-up. The HUB monitoring
server does not shutdown gracefully and just hangs. This affects the
FTO environment. Since the HUB is not shutting down gracefully,
agents and RTEMS are not switching to other FTO HUB. |
| IV74705 | When using tacmd createsit to clone another situation, the values
of the MAP tags are not preserved. |
| IV78188 | The maximum timeout that an administrator can specify with the
"-t" option in the "tacmd login" command may be too high for some
customer security policies. This APAR introduces the possibility to
reduce the maximum timeout to only 15 minutes in a centralized way.
In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IV78192 | The tacmd commands getfile, putfile and executecommand need to
log their actions into the TEMS audit log file. Specifically the
following info will be logged when this APAR is applied: username, executed command, result, source and target servers. |
| IV78398 | tacmd commands that manage the situations are not processing all
the situations after the upgrade of the ITCAM agent affinities. With
the ITCAM Agent for WebSphere Applications 07.20.00.05 installed,
there are error on the tacmd commands that work with the situations.
In particular with the situations that has affinity like
&IBM.CAM7_WAS or &IBM.CAM_WAS, issuing any of the following
commands return error on the situation definintion: tacmd bulkimportsit tacmd bulkexportsit tacmd listsit tacmd createsit tacmd editsit tacmd viewsit tacmd deletesit |
| IV82136 | Running the "tacmd viewuser" CLI command returns a
java.lang.NullPointerException ./tacmd viewuser -i <USER_ID> Exception in thread "main" java.lang.NullPointerException at com.ibm.tivoli.itm.user.viewUser.run(viewUser.java:1235) at com.ibm.tivoli.itm.user.viewUser.jnimain(viewUser.java:1260) |
| IV82236 | On AIX, when the ue(tacmd) and portal server component are
installed in the same CANDLE_HOME, the TACMD EXPORTWORKSPACES
command does not search in local portal server directories where are
stored JAR resource files. This issue causes a memory leak on local
or remote HUB TEMS server because of the continuous requests from
TACMD client to the TEMS HTTP SERVER on port 1920 to get these JAR
resource files instead of having these JAR resource files locally
stored just one time. The command TACMD EXPORTWORKSPACES itself
completes successfully because the JAR resource files are always
retrieved from the cache if they are not available locally on the
system from which TACMD EXPORTWORKSPACES command is issued. |
| IV82922 | When using tacmd executecommand with a command longer more than
64 characters or tacmd getfile and tacmd putfile with a source or
target file longer more than 64 characters, the command crashes. |
| IBM Monitoring Agent for Linux OS APARs | |
| IV74388 | The Monitoring Agent for Linux OS running on zLinux needs to
collect the output of the "vmcp q userid" command in order to build
a portion of the Virtual Machine Identifier attribute value. The
vmcp command could be installed in a directory that is not defined
in the PATH variable of the agent environment, so the agent could
miss to find it thus producing an incomplete value for this
attribute. Since this attribute is a key identifier of the system
this could lead to wrong results in integration scenarios with other
products. |
| IV78033 | Due to a lack of synchronization with the internal thread that
collects data for the "Disk Usage Trends" attribute group it may
happen that the agent hangs while responding to a query or a
situation on the "Linux Disk" attribute group, as the two groups
share the same object. The event is rare because the "Disk Usage
Trends" thread runs only once per hour by default. |
| IV78315 | All of the attributes defined as percentages in the Linux NFS
Statistics attribute group of the Monitoring Agent for Linux OS,
like Get Attribute Calls Percent, may report negative or huge values
because of possible 32 bit integer overflows during their
computation. |
| IV78556 | The Monitoring Agent for Linux OS may report incorrect values for
the following attributes in the Linux Process attribute group, when
they exceed 100%: Process System CPU (Percent), Process User CPU (Percent), Cumulative Process System CPU (Percent), Cumulative Process User CPU (Percent), Process Busy CPU (Percent) and Cumulative Busy CPU (Percent) These attributes can exceed 100% on servers with multiple online processors. Also, these attributes are not normalized to the number of online processors, thus preventing 100% to be exceeded, whereas other CPU-related attributes in this group are normalized. In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IV79424 | The Monitoring Agent for Linux OS does not provide any
information about the time when a process was started, nor for how
long it has been running. |
| IV79807 | Monitoring Agent for Linux OS shows as 'not available' the number
or runnable and blocked processes in the Linux VM Stats attribute
group even if they are present in the file /proc/stat, due to a
problem with the buffer size while reading them. |
| IV80542 | The Monitoring Agent for Linux OS can randomly crash during Disk
attribute group data collection. This is due to a memory corruption
caused by a timing condition between two agent internal threads.
This condition may occur when one or more filesystems do not respond
within the 2 seconds default timeout for the statfs64 system call. |
| IV82704 | The Monitoring Agent for Linux OS estimates the physical memory
actually available to the system for starting new applications
without swapping by using a simple algorithm that takes into account
freeable memory contributions like memory in cache and memory in
buffers. Since kernel 3.2 the same information is directly computed
by the system, in a more accurate way, and made available through
the specific MemAvailable field in the /proc/meminfo file, as well
as in the new column "available" of the "free" command output. |
| IV83672 | The Monitoring Agent for Linux OS returns an empty data row in
the Custom Scripts Runtime Sampled attribute group even if the
configured custom script does not produce any output rows. This is
not consistent with the equivalent pure event attribute group,
Custom Scripts Runtime, that returns no rows in such a case. Also,
situations based on the number of expected rows may trigger
improperly. |
| IV84786 | The Monitoring Agent for Linux OS only provides the possibility
to choose whether or not NFS and CIFS filesystems must be monitored.
Any other types cannot be excluded. In case of a large number of
filesystems of the same type that don't need to be monitored, this
limitation can introduce performance issues on the agent. In order
for this APAR to be properly implemented in your environment, a new
environment variable has been added. See the "Install Actions"
section of the APAR conclusion for more details. |
| IV85805 | The Linux Sockets Detail and the Linux Sockets Status attribute
groups in the Monitoring Agent for Linux OS only report information
about IPV4 sockets. |
| IV87359 | This is a follow-up of APAR IV73936 that fixed a temporary
condition where the Monitoring Agent for Linux OS was awakened by
signals while sleeping between two consecutive samples for the Linux
CPU attribute group, thus reporting invalid processors' CPU
percentages. This APAR also fixes a condition where signals are
permanently interrupting the polling threads and applies to the
following attribute groups in addition to the Linux CPU one: Linux
System Statistics, Linux Swap Rate, Linux Process, Linux Network,
Linux Disk IO, Linux IO Ext, Linux TCP Statistics. |
| IBM Monitoring Agent for Unix OS APARs | |
| IV68775 | On AIX and HPUX, when the Monitoring Agent for UNIX OS is
started, two files are created with 777 permissions. The file is an
internally used file for socket communications under
$CANDLEHOME/<arch>/ux/bin/pasipc directory. |
| IV74123 | The RAS1 log file for the kcawd process on the Monitoring Agent
for UNIX OS filling up with "agent list size" messages. The messages
can be ignored and should not be written to the log file at ERROR
tracing. This can also occur with Monitoring Agent for Linux OS and
Windows OS. |
| IV74490 | RAS1 logs of the Monitoring Agent for UNIX OS at the default
ERROR level may become unreadable due to a repeated couple of error
messages printed while monitoring processors on the Solaris
platform: vm_stat_externals.cpp,1757,"get_cpu_stats") kstat_lookup error - (cpu_stat,123,NULL) vm_stat_externals.cpp,1758,"get_cpu_stats") kux_vmstat does not collect cpu123 information These messages are printed for each disabled processor, every thirty seconds. |
| IV75662 | The attribute Mount_Point_U of the group UNIXDISK is not defined
as primary key. This prevents its use with performance analyzer as
it needs 2 primary keys. |
| IV77124 | The File System Type attribute in the Disk attribute group of the
Monitoring Agent for UNIX OS cannot be used in situations that alert
on remote filesystems becoming unavailable. This kind of information
is always locally available and it does not get lost when the remote
filesystem becomes unreachable. Nevertheless the agent returns it as
Not Collected. |
| IV77559 | The data gathered executing the custom scripts in 6.30 FP5 are
reported using the KXX_Custom_Scripts_Runtime attribute groups.
These groups implement 'pure event' tables. Because of this,
situations cannot receive 'clearing' events and need to be manually
closed. |
| IV79257 | After the upgrade to 6.30 FP5 the Summarization and Pruning Agent
starts failing to add new rows to the hourly, daily, weekly,
monthly, quarterly and yearly summarized tables for the "Disk"
attribute group in a DB2 Data Warehouse. This is because of new
columns added to these tables' definitions that make their size
cross the DB2 legacy 4Kb limit. |
| IV79797 | The Monitoring Agent for UNIX OS can randomly fail to determine
the arguments associated to the command line of a running process.
In such a case it may assign to a process the command line of
another process, because of missing memory initialization in the
error code branch. Situations based on the Process.Process_Command
attribute can then trigger/not trigger improperly. |
| IV80830 | A condition has been identified where
the buffer containing data for a filesystem can be overridden
by those for another filesystem. This memory corruption is
caused by a timing condition between two agent internal threads
and it may occur when one or more filesystems do not respond
within the 2 seconds default timeout for the statvfs64 system
call. |
| IV81209 | The attribute Mount Point (Unicode) in the Disk attribute group
of the Monitoring Agent for UNIX OS cannot be chosen as a legend
label in Tivoli Enterprise Portal plot chart views, due to an
internal illegal definition. |
| IV81845 | Monitoring Agent for UNIX OS becomes unresponsive on AIX due to
an incomplete response of the AIX api perfstat_netinterface |
| IV84770 | On Solaris x86 11.3, the Monitoring Agent for UNIX OS will crash
or will not stop without the force option (-f). The problem is not
seen prior to Solaris 11.3. The agent is crashing just after startup
with the stacktrace seen below, however the processes can continue
to run. In the <hostname>_ux_<999999999>.log file, the following stacktrace is seen: **** Stacktrace in standard logs. Enable KBB_SIG1=-dumpoff in ini for core dumps **** /opt/IBM/ITM/sol606/ux/bin/kuxagent'stacktrace_handler+0x5b [0x7384fb] /lib/amd64/libc.so.1'__sighndlr+0x6 [0xffff80ffbf4f8636] /lib/amd64/libc.so.1'call_user_handler+0x2ce [0xffff80ffbf4eb68e] /usr/lib/amd64/libCstd.so.1'__1cDstdMbasic_string4Cwn0ALchar_traits4Cw__n0AJallocator4Cw___Fempty6kM_b_+0x7 [0xffff80ffbdbb99d7] [Signal 11 (SEGV)] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cOGetCommandLine6Fi_nDstdMbasic_ string4Cwn0ALchar_traits4Cw__n0AJallocator4Cw_____+0x679 [0xffff80ffb1561379] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cNKcaCmdSolarisPopenApplication6MrnDstdMbasic_string4Cwn0BLchar_traits4Cw__n0BJallocator4Cw____23ri3pnGPolicy__pv_+0x416 [0xffff80ffb154b0b6] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cKKcaCmdUNIXUgetAppOperatingStat e6MnDstdMbasic_string4Cwn0BLchar_traits4Cw__n0BJallocator4Cw____22ripnGPolicy__nPOperatingStates__+0x194 [0xffff80ffb1539fe4] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cIWatchdogRgetOperatingState6M_nPOperatingStates__+0x2d7 [0xffff80ffb14c3477] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cKControllerWProcessMgmtStateChange6MpnOAgentMgmtEvent__v_+0x12f6 [0xffff80ffb146cfc6] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cKControllerbEupdatePersistedAgentCollection6MrnSManagedProcessList_pnGPolicy__v_+0x584 [0xffff80ffb1464c44] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cKControllerVProcessCAPStateChange6MpnMCAPFileEvent__v_+0x34f4 [0xffff80ffb146a044] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cMCAPFileEventTdoCommandProcessing6M_v_+0x24c [0xffff80ffb14e7b8c] /opt/IBM/ITM/sol606/ux/lib/libkca.so'__1cOCommandHandlerKrunHandler6M_v_+0x3f4 [0xffff80ffb14db4d4] /opt/IBM/ITM/sol606/ux/lib/libkca.so'commandHandlerThreadEntry+0xf7 [0xffff80ffb14db057] /lib/amd64/libc.so.1'_thrp_setup+0xa5 [0xffff80ffbf4f8269] /lib/amd64/libc.so.1'_lwp_start+0x0 [0xffff80ffbf4f8510] Fatal Error (11) Detected. Exiting |
| IV90059 | The ifstat daemon can hang when calling the "netstat" or
"namerslv" commands. The agent continues to run, however the data
collection part of the agent stops collecting metrics. This APAR
allows the Monitoring Agent for UNIX OS to not collect Gateway and
Domain attributes. These attributes were introducted in version
6.3.0 FP2 and are valid on AIX-only. The AIX commands used to
collect these metrics can sometimes hang resulting in the agent no
longer being able to collect data. With tracing set to (UNIT:if ALL), the <hostname>_ux_ifstat_<999999>-<nn>.log shows the last line is executing the netstat command (for Gateway) or namerslv (for Domain) which never returns: (2016/09/28,01:57:37.000D-1:ifstat-bsd.cpp,278,"fillGatewayMap") COMMAND: LANG=C; LC_ALL=C; /usr/bin/netstat -r -n -OR- (2016/10/14,13:07:48.0005-1:ifstat-bsd.cpp,235,"getDomain") COMMAND: LANG=C; LC_ALL=C; /usr/sbin/namerslv -s 2>/dev/null In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IBM Monitoring Agent for Windows OS APARs | |
| IV67483 | If the memoryThreshold value is set in the
kntcma<_default>.xml file, and the memory working set size
exceeds a 32-bit value, the OS agent will be restarted as it will
determine the memory threshold has been exceeded. The Windows OS Agent RAS1 log file will contain a message simlar to the following. Note the memory usage is listed as a negative number. kcawd.cpp,661,"checkHealth") Agent <kntcma> PID <####> will be restarted; memory usage <-2147483648> exceeded threshold of <##########> The Problem was reported against the Windows OS agent; the code was updated to support 64-bit values for the Monitoring Agent for Windows OS as well as the Monitoring Agent for Linux OS and Monitoring Agent for UNIX OS. |
| IV69861 | On some Windows systems, the Monitoring Agent for Windows OS
cannot be stopped due to the executable kcasc.exe hanging
periodically. This executable is called when Watchdog is being
disarmed which needs to occur before the OS Agent can be stopped.
This was seen on a Citrix server. |
| IV73966 | The Monitoring Agent for Windows OS does not have an attribute
showing the drive type in the Logical Disk attribute group. |
| IV77564 | The Monitoring Agent for Windows OS does not set the port for FPC
Daemon when other properties files are present in the same path of
kfo_cps.properties |
| IV78199 | The Monitoring Agent for Windows OS terminates when the Agent
Management Services workspace is selected and the Agents' Alerts
view has one or more alerts listed that are more than 24 hours old.
The problem occurs when the code tries to delete the alerts older
than KCA_CACHE_LIMIT (default is 24 hours). The crash does not
happen every time. In the Windows OS Agent RAS1 log file with KBB_RAS1 tracing set to (UNIT:KCA ALL), will see the following message towards the end of the log file (5625AD92.02AD-2C10:kntpaagt.cpp,330,"TakeSample") About to delete |
| IV78528 | "Top Resources UtilizationSummary Heat Chart" fails with an
arithmetic overflow exception due at large amount of data and large
values, with this message error: An error occurred while performing operation 'sqlScrollBulkFetch' status='-232'. RQP-DEF-0177 An error occurred while performing operation 'sqlScrollBulkFetch' status='-232'.UDA-SQL-0144 An arithmetic exception was detected.[IBM][CLI Driver][DB2/LINUXX8664] SQL0802N Arithmetic overflow or other arithmetic exception occurred. |
| IV80998 | While processing situations on the File Trend attribute group the
Monitoring Agent for Windows OS may print excessive information
about missing files in its RAS1 logs at the default ERROR level. |
| IV82178 | The Monitoring Agent for Windows OS does not show the Binary Path
in Processes Attribute Group when running as non-administrator. In
order for this APAR to be properly implemented in your environment,
a new environment variable has been added. See the "Install Actions"
section of the APAR conclusion for more details. |
| IV83118 | The Monitoring Agent for Windows OS does not show clearly in the
logs the service name and the error message when it does not succeed
in opening a service (for example due to a restricted access). |
| IV83694 | The Monitoring Agent for Windows OS shows 2147483647 in the
attribute System Up-Time of the system Attribute Group when the
system time is changed to a value before the effective start. |
| IBM Monitoring Agent for IBM i APARs | |
| IV87940 | Message situation using SELECT == *MNR results in two alerts. The
first alert is sent when an inquiry message is received on the
message queue. The second alert is sent when a reply to the inquiry
message is sent. This is a behavior change from an earlier release
and does not match the documentation. For SELECT == *MNR, the
desired behavior is a single alert when the inquiry message is
received on the message queue. |
| IV90312 | Distribution queue or history log situations or reports fail with
CNB7007 error message and the agent job log contains a CPF4167 which
indicates that the job cannot create any more spool files. The error
does not occur immediately after starting the agent. Instead, the
error occurs after the agent has been running for long time (i.e.
several days or weeks). In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IBM Tivoli Enterprise Monitoring Agent APARs | |
| IV78703 | Program signature violation while IBM i MQ Agent starts on IBM
ISeries. During initialization, LIBKT1KRA points to library (i.e.
directory) QAUTOMON, which is the correct location for the IBM i OS
agent, but not for the IBM i MQ Agent. |
| IV81217 | When events are being sent to an EIF Receiver and the error code
0x1DE0000B is received, the events do not get forwarded. Error code
0x1DE0000B means inbound disconnect, meaning when the event was to
be sent the session had already been disconnected by the peer. This
was seen in an environment where HAProxy was used as the EIF
Receiver. |
| IBM Tivoli Enterprise Monitoring Installation APARs | |
| IV70885 | For remote deploy update agent, additional disk space is required
in CANDLEHOME. The Monitoring Agent for UNIX OS prereq check
configuration file needs to be updated to more accurately reflect
actual disk space requirements. |
| IV74708 | When configuring the Portal Server as a non-root user while it is
running, the following message is incorrectly displayed: Component can not be managed due to insufficient privileges. |
| IV76877 | The OS agent will not connect using IP.SPIPE after running
"SetPerm -a" or "secureMain lock" on HP-UX. IP.SPIPE or any ssl
based protocol is not initialized on HP-UX when the agent binary is
owned by root with the SUID bit turned on and the agent is launched
from a non-root ID. In the agent RAS1 log you see entries like the following in the log header when you are launching the agent in this way: +55EA18D8.0000 Program Name: kuxagent User Name: itmuser +55EA18D8.0000 Effective User Name: root The GSKit has failed to initialize when you can find the following string: "Active Shared Libraries". The GSKit has successfully initialized when you find the following string: "GSKit Environment" |
| IV78498 | IV65616 added RHEL7 support for regular components in 6.30.03.00.
That APAR neglected to cover System Monitor Agents (SMA). |
| IV80564 | For a pristine install, if the installation image does not
contain the file kcirunas.cfg, the install process ends with the
message "install.sh failure". There is no indication as to the
nature of the failure. |
| IV80618 | Performing monitoring server seeding on a Remote monitoring
server causes the SQL to be processed at the HUB monitoring server
instead, restarting the MS_OFFLINE situation causing new alerts for
numerous known off-line systems. |
| IV81349 | On some Windows machines, the installer goes into an endless loop
reading dummy_files_list.txt. The operating system fails to signal
end of file while the installer is reading dummy_files_list.txt.
This causes the installer to continually read without ever stopping.
Eventually, the install log is filled to capacity and the install
process is aborted, or the customer cancels the install. |
| IV82690 | For some locales that do not recognize daylight saving time, the
reported current time in the KinCInfo header may be off by one hour.
Locale developed time is performed by an IBM Tivoli Monitoring call
to NLS code which may fail for locales that do not recognize
daylight saving time. |
| IV82700 | The Java Attach API is a mechanism provided by the Java Runtime
Environment (JRE). It is designed to allow applications to connect
to a running Java Virtual Machine (JVM). The interface is described
here: http://www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.zos.70.doc/user/attachapi.html By default, Java creates a directory and file structure like this the first time a JVM is started: drwxrwxrwt TMPDIR/.com_ibm_tools_attach -rw-rw-rw- TMPDIR/.com_ibm_tools_attach/_attachlock -rw-rw-rw- TMPDIR/.com_ibm_tools_attach/_master -rw-rw-rw- TMPDIR/.com_ibm_tools_attach/_notifier It also creates a directory and file structure like this for each running JVM: drwx--x--t TMPDIR/.com_ibm_tools_attach/<PID> -rw-rw-rw- TMPDIR/.com_ibm_tools_attach/<PID>/attachNotificationSync -rw------- TMPDIR/.com_ibm_tools_attach/<PID>/attachInfo Note: For AIX and Linux, TMPDIR is usually /tmp. For Windows, TMPDIR is usually C:\Users\<userid>\AppData\Local\Temp or a subdirectory within. While no application data is stored here and the structure is recreated if it is ever destroyed, some perceive the permissions structure to be a security exposure. This behavior exists for IBM Tivoli Monitoring (ITM) on AIX, Linux, and Windows. Neither HP-UX nor Solaris are affected. |
| IV82980 | Windows OS Agent (KNT) does not start after upgrade to 6.3.0 FP5.
File PSAPI.DLL in the Windows directory, the ITMHOME\InstallITM,
ITMHOME\CMS, and ITMHOME\TMAITM6 directories is not compatible with
Windows 2008 and above. |
| IV83251 | The Java Runtime Environment (JRE) that is installed by IBM
Tivoli Monitoring is upgraded as follows: - 1.7.0 SR9 FP50 for CANDLEHOME on AIX, Linux, Solaris, and Windows - 1.6.0 SR16 FP30 for CANDLEHOME HP-UX - 1.7.0 SR9 FP60 and 1.6.0 SR16 FP30 for Tivoli Enterprise Portal (TEP) browser clients. |
| IV83880 | On Windows, the IBM Tivoli Monitoring (ITM) installer updates the
PATH value to include ITM directories. Before doing so, ITM computes
the maximum PATH length and aborts the install if the updated PATH
will be more than Microsoft supports. When this happens, ITM
displays a popup with the following message: PATH environment variable length exceeds the maximum, abort install. See Microsoft Knowledge Base KB180410, KB906469, and KB832978. In addition, CANDLE_HOME\InstallITM\Abort IBM Tivoli Monitoring yyyymmdd hhmm.log contains messages similar to these: mm-dd-yyyy hh:mm:ss OSMajor(6) OSMinor(1) MaxPath(2047) mm-dd-yyyy hh:mm:ss PATH environment variable length exceeds the maximum of 2047, abort install. See Microsoft Knowledge Base KB180410, KB906469, and KB832978. Microsoft has published new hotfixes, service packs, and versions that extend the previously known maximum PATH length. ITM should account for these updates. |
| IV83886 | The prerequisite scanner can be run optionally under install.sh
as part of the install process. When run this way, install.sh writes
results information in the form of console messages. This results
information includes the product name. If the two-character product
code contains a numeric digit, the product name or description is
not displayed. |
| IV85142 | The IBM Global Security Kit (GSKIT) shipped with IBM Tivoli
Monitoring will be uplifted to version 8.0.50.69. |
| IV85156 | On UNIX and Linux, the secureMain utility controls access to IBM
Tivoli Monitoring components. The Tivoli Enterprise Monitoring Agent
(TEMA) component used by all agents creates a set of files in
<CANDLEHOME>/<platform>/<pc>/bin. These data files
require group write access for the agent to run properly. When
secureMain is used to set permissions for the component, these files
are set with group read only access. The file name patterns affected
are: psit_*.str, *_agntstat.sta, *_autoattr.asa, and
*_thresholds.xml. When this happens, messages like the following are written to the agent log: (531F0D57.0087-B:kraapsit.cpp,1169,"writePersistSituation") Unable to open file /opt/IBM/ITM/ls3263/mq/bin/psit_XXXXXXX_xxxxxxxx_XX.str for recording, error=13 |
| IBM Tivoli Enterprise Monitoring Server APARs | |
| IV67432 | The online/offline status of the portal server connected to the
standby HUB is inaccurate. It can report as online when it is
offline. It can also report as offline when it is online. |
| IV70874 | Master reset event sent not clearing situations in ONMIbus opened
from previously active hub monitoring server in a hot-standby
scenario. In order for this APAR to be properly implemented in your environment, the Event Synchronization from the IBM Tivoli Monitoring (tec) 6.3.0 FP7 install image needs to be installed. See the "Install Actions" section of the APAR conclusion for more details |
| IV71275 | When situations use multiple attribute groups, the event class
name for the forwarded event may be determined incorrectly. |
| IV71397 | Configuring the Monitoring Server with a connection list that
exceeds to total length of 100 characters will result in the putfile
command overwriting the temporary character array, and memory,
resulting in a memory access error. The memory access error causes
the tacmd program to abnormally terminate. |
| IV77557 | Tivoli Enterprise Monitoring Server queries for CT_Affinity using
product code returns incomplete list of affinities. This can result
in various tacmd commands to not process correctly, for example
tacmd listsit or tacmd bulkexportsit are not listing/exporting all
defined situations for some product codes. ITCAM Agent for WebSphere Applications 07.20.00.05 is an example. Issuing any of the following does not list/export all YN situations, specifically those situations that have affinity of &IBM.CAM7_WAS or &IBM.CAM_WAS ==> tacmd listsit tacmd bulkexportsit -t yn -d or tacmd bulkexportsit -d |
| IV81149 | The customer's security policy requires that the Tivoli
Monitoring server / AIX password encryption algorithm be changeable
from 'crypt' to 'sha256' for user validation at the Tivoli
Monitoring server. |
| IV81199 | In a FTO environment, the Acting hub monitoring enterprise server
is always enabled for receiving and processing SOAP requests.
Submitting SOAP requests to a Mirror hub monitoring enterprise
server is not permitted; this restriction is a safeguard to prevent
Mirror hub monitoring enterprise server from getting out of sync
with the Acting hub monitoring enterprise server in an FTO
environment. |
| IV82177 | Submitting multiple event map updates consecutively without delay
can result in the HUB Tivoli Enterprise Monitoring Server shutting
down. This problem is not likely to occur when only a small number
of event map updates are made. This problem will not occur if event
forwarding is not used. This problem is not common. It is most likely to occur if there are hundreds of event map updates being done sequentially. This has only been seen in FTO synchronization thus far, but this is not FTO specific. This problem can confirmed by seeing the following in the TEMS log: ...kglkycbt.c,841,"kglky1rs") Unknown isam rc = -4 ...kfaibloc.c,813,"IBL_Process") Error: KEY1 failed with rc <8> ...kdsstc1.c,1658,"ProcessTable") ProcessTable Locator status = 64 ...kdsvws1.c,2421,"ManageView") ProcessTable EVNTMAP Select Error status = ( 64 ). KFAOMTEC ...kdsrqc1.c,2624,"AccessRowsets") Could not obtain rowset 2, status code = 64 ...kfaoteib.c,685,"Get_User_Map_Entry") Unable open event map request. status <64> ...kfaoteib.c,699,"Get_User_Map_Entry") Exit: 0x8 |
| IV87174 | These 'false' messages are benign. In spite of the 'false' error
messages, the intended functional behavior of the code is performing correctly. However,when these 'false' messages do occur there are large numbers of the message appearing in TEMS RAS1 log files. Here is example of message at issue ==> ~ ~ ~ ***ERROR: for RRN <1883>, (oldest) Index TS < !m?? > does not match TSITSTSH TS <1160704131915110> ~ ~ ~ |
| IV88750 | The new situation take action command, ZOSWTO, will cause a
multi-line WTO to be issued on the z/OS monitoring server that an
agent is connected to or on a z/OS agent. The message will be
produced when the situation is true or false. The message ID will
always be KO41041I. Any data that follows the command name, ZOSWTO,
will be present in the multi-line WTO. When the situation is false
the values of substitution variables will be NA. The format of the
message will be as follows: KO41041I SITUATION EVENT ZOSWTO situation_name:node_name<optional_display_item_value> T/F customer_supplied_command_data The actual message data will be broken up into 70-character sections on a maximum of 5 consecutive lines. By default, Descriptor code 12 and route code 2 are used by the WTO operation. These can be changed by specifying ZOSWTO_DESCRIPTOR_CODE and ZOSWTO_ROUTE_CODE in KBBENV. Multiple codes may be specified using comma separated values. |
| IBM Tivoli Enterprise Portal Client APARs | |
| IV67096 | When using the portal client through WebSEAL, clicking the
"Logout" link does not display the WebSEAL logout page. This only
occurs when using the browser version of the portal client. In order for this APAR to be properly implemented in your environment, a new client property has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IV73844 | The tivoli portal client contained some java script that is used
to scub URI's of HTML tags. This java script function and the
regrular expressions used to do the scrubbing was found to be
vulnerable to attacks. |
| IV77112 | As of Java 8 u60 the java webstart process started throwing parse
errors when processing the tep.jnlp file. Oracle introduced a new
xml parser in the webstart process. |
| IV77742 | Currently when a Tivoli Portal user has "Take Action" authority,
the dialog used for passing arguments with an action ('Edit Argument
Values' pop-up ), command allows for inclusion of additional
characters in the text field. By this APAR fix, the administrator is
able to list the characters that are not allowed in this field. In order for this APAR to be properly implemented in your environment, a new environment variable has been added. See the "Install Actions" section of the APAR conclusion for more details. |
| IV77992 | A security vulnerability exists between the Tivoli Enterprise
Portal client and the Tivoli Enterprise Portal Server in regard to
user authorization. It was found that a mailicious attacker could,
in principle, modify the information being transferred between the
client and server in such a manner as to modify the user's
authorization assignments associated with their user profile. NOTE: The fix for IV77992 requires the patch be installed on the portal server. In addition to this, the patch needs to be installed on the systems where the tacmd CLI is installed and utilized. The CLI is installed as part of the "ue" component. |
| IV82891 | When user selects a row of data in a table view and then select
the "take action" menu item, it lists all of their systems. By this APAR, it will list only the managed system that is found in that row of data. |
| IV89128 | The Tivoli Monitoring 6.3.x Tivoli Enterprise Portal browser
client stopped functioning when launched using the Firefox browser
from a Windows OS client. The following behaviors have been observed: 1. Tivoli Enterprise Portal applet will not launch at all; no deployment of the applet by the browser occurs. 2. Tivoli Enterprise Portal applet will launch, but will then crash; a message reporting that the Java deployment toolkit had failed is displayed. 3. Tivoli Enterprise Portal applet will launch, and the logon dialog will appear; however, after entering valid user credentials, the applet will repeatedly restart itself, and the first workspace will never be rendered. 4. Tivoli Enterprise Portal applet will launch, and first workspace will render successfully; however, after just a few attempts to switch to other workspaces from the navigator view, the content area will disappear, and only the applet's top banner frame will be displayed. |
| IV89461 | More recent Java runtime releases from Oracle have maintenance
levels that are greater than 99. An example would be Java 8u111
(release 1.8.0_111). One of the components packaged with the Tivoli
Enterprise Portal requires that the maintenance level be < 100 in
order to function properly. This component is responsible for the
rendering of many graphical views in the Portal, including the
Policy Workflow Editor, Graphic Views in workspaces, and Situation
Formula display. If the Java runtime maintenance level is > 99,
then access to these features in the Portal will fail, and the
Portal client can become unstable. |
| IBM Tivoli Enterprise Portal Server APARs | |
| IV80202 | The payload returned by the IBM Tivoli Monitoring Dashboard Data
Provider for metric requests includes metadata information used by
the dashboard widgets to calculate the displayed value. For
percentage type attributes, this additional metadata includes the
maximum range that the value can attain for the attribute. In some
scenarios, that maximum range value was not computed correctly by
the Dashboard Data Provider. This resulted in the displayed value on
the dashboard being formatted incorrectly, where the decimal
position was off by a factor of 10 or more. |
| IV80745 | Tivoli Enterprise Portal Server crashes after Windows Server
reboot. The portal server is started automatically when Windows
starts, but when the first portal client attempts to connect, the
portal server crashes and generates a crash dump. The stack dump
contains the following: KfwMain!CTRefString::CTRefString+0x30 KfwMain!CTPropertySequence::fetchPropertyBool+0x2d KfwMain!CTReport::Query::Data::modelHeader+0x336 |
| IV82531 | This display issue will occur under the following conditions: 1) The customer is viewing a dashboard constructed and displayed using DASH. 2) The dashboard displays timestamp atributes where the value originally provided by the monitoring agent contains all zero digits. Under these two conditions, the value of the timestamp shown in the dashboard will be "1999-11-30 00:00:00". This issue was originally reported for application data associated with the OMEGAMON for Mainframe Networks product. The timestamp attributes are "HWMTM" (Active Connections High Water Mark Timestamp) and "BCKLOGRETM" (Backlog Connections Rejected Timestamp). However, any data provided by any ITM monitoring agent that satisfies the two conditions listed previously will also be displayed with the same erroneous timestamp value in the DASH dashboard; so this issue is not restricted to the OMEGAMON for Mainframe Networks solution. In addition, this problem is not restricted to any particular server platform, but applicable to all platforms supported by the ITM TEPS component. |
| IV83285 | When an agent is offline and the portal server disconnects from
the HUB Tivoli Enterprise Monitoring Server followed by the TEPS
connecting to the HUB Tivoli Enterprise Monitoring Server again, in
the navigator tree, the chid items associated with the offline agent
ar no longer gred out. Clicking on the child items results in the
workspace pane displaying the message "KFWITM454E Request failed due to offline manage systems(s)". |
| IV83613 | This CPU utilization problem can sometimes be observed when the
Hybrid Gateway is used to retrieve agent metric information from
agents at different version levels. |
| IV83775 | Portal server randomly crashes after applying 6.3.0 FP6. The eWAS
SystemOut.log will show one of the following errors: java.lang.NullPointerException at com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JDBCDataSource.java:541) or: java.sql.SQLException: Closed Resultset at oracle.jdbc.driver.ScrollableResultSet.next(ScrollableResultSet.java:311) at com.ibm.TEPS.CTSQLJDBC.JDBCDataSource.pullSequenceWithTimeout(JDBCDataSource.java:538) The exception occurs when trying to run a query to a JDBC data source (such as an Oracle warehouse database). If the query takes a long time to run, and the user switches to a different workspace before the JDBC query finishes, the crash will occur. |
| IV90475 | The Visibroker libraries have been uplifted to address
CVE-2016-6304 in OpenSSL when OSCP Stapling feature is used. The
protal server does not explicitly use the feature but we are
uplifting the libraries to cover the latest vulnerability. |
| IBM Tivoli Monitoring OS Agents Reports APARs | |
| IV74074 | In case of servers with multiple network interfaces, the DNS name
used to build the ManagedSystemName column and the one assigned to
the FullyQualifiedHostname column in the TDW ManagedSystem table may
belong to different network interfaces and thus do not match. This
can produce an incorrect list of servers when running OS agent
reports. |
| IV78822 | OS Agent's, "Top resources by availability" report, fails with an arithmetic overflow exception due to a large amount of data and large values with this message error: RQP-DEF-0177 An error occurred while performing operation 'sqlScrollBulkFetch' status='-232'. UDA-SQL-0144 An arithmetic exception was detected.[IBM][CLI Driver][DB2/AIX64] SQL0802N Arithmetic overflow or other arithmetic exception occurred. |
| Performance Analyzer APARs | |
| IV90871 | The problem happens on ITPA version 06.30.03 - 06.30.06. The
'Performance Analyzer Agent Moswos' attribute group 'Version'
attribute has incorrect value '06.30.02'. You can click 'Performance
Analyzer Warehouse Agent' navigator node, go to 'Performance
Analyzer Agent Statistics' workspace 'Agent Statistics' workspace
view, check 'Version' attribute, it displays incorrect value
'06.30.02'. This problem is fixed in ITPA version 06.30.07. |
| Summarization and Pruning Agent APARs | |
| IV79900 | Summarization and Pruning agent fails to create partitioned
tables for various agent attribute groups. Error message seen in the SY Workspace: Tablespace "ITMREG8K" is not compatible with tablespace "TS_INDX_4K_01". Reason code = "3" SQLCODE=-1860, SQLSTATE=42838 Driver=4.14.137 |
| IV80032 | The Summarization and Pruning agent, as part of its normal purge
processing, Drops tables from the Database Server. The DB2 Database
Server performs Table Drop functions asynchronously. If the
Summarization and Pruning Agent is terminated (Detached) by the user
before the DB2 Database Server has completed its Drop processing,
the Tables are left in an indeterminate state by DB2. When the
Summarization and Pruning Agent is restarted, those Tables which
were to have been Dropped reappear, and their status does not make
it possible to clean up the Table status conflict. As a result the
Summarization and Pruning Agent does not start (hangs). |
| IV81519 | The HTTP and HTTPS protocols are not supported by the KSY Agent
to connect to the Portal Server. See this Technote
for more details. |
| Warehouse Proxy Agent APARs | |
| IV80194 | When starting the WPA agent, any variables defined in the
config/hd.environment file are ignored. |
| IV83437 | Monthly Paritions are not created if the Summarization and
Pruning Agent is dormant (remains in a stopped state) for a time
that exceeds the user configuration value of "Number of future
partitions to maintain". |
Problems originally corrected in IBM Tivoli Monitoring 6.2.3 Fix Pack 5 (cumulative) have also been corrected in 6.3.0 Fix Pack 4 and later.
Tivoli Monitoring maintains a Technote that describes the APAR parity between all recently released fix packs across releases of IBM Tivoli Monitoring version 6, namely versions 6.1.0, 6.2.0, 6.2.1, 6.2.2, 6.2.3, and 6.3.0.
Refer to this Technote for additional information:
http://www.ibm.com/support/docview.wss?uid=swg21358804
| January 06, 2017 | Original version |
| January 16, 2017 | Minor correction incorrect APAR link. |
| January 16, 2017 | Clarification on Ubuntu support. |